chore: add last transition time metrics#203
Merged
Merged
Conversation
mattdjenkinson
approved these changes
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
To support dashboarding of resource health over time we need to know when conditions last changed, not just their current value. This adds
status_condition_last_transition_timegauge metrics for the four resources that previously only hadstatus_conditioncoverage.Changes
New generator blocks in
config/resource-metrics-policies/networking-metrics.yaml:datum_cloud_network_status_condition_last_transition_timedatum_cloud_subnet_status_condition_last_transition_timedatum_cloud_subnet_claim_status_condition_last_transition_timedatum_cloud_networking_http_proxy_status_condition_last_transition_timeEach block iterates
status.conditions, emitsdouble(timestamp(item.lastTransitionTime).getSeconds()), and carriesname,namespace,condition,reason,statuslabels — consistent with the existing pattern on Domain, Gateway, and Backend.